This chapter describes an example IFS-strategy that is a good guideline for external and internal websites.
Units
The root of the IFS contains of the following units:
| Unit | Description |
|---|---|
| Admin |
Contains code, controls, CSS, editing templates, presentation templates - all functionality
of the website built and managed in the Admin unit. Only administrators and developers should be able modify this content. |
| Configuration | Modules to manage configurable elements on the website. Mainly intended for administrators. |
| Eng | English documents and templates for editors. Document categories with different functionality and appearance should be divided into separate categories. |
| Sve | Swedish documents and templates for editors. Document categories with different functionality and appearance should be divided into separate categories. |
Admin categories
The admin unit typically consist of two categories:
- Shared which contain shared resources that are used throughout the website.
- Modules that are used to support specific parts of the web site. Examples: News, Articles, Voting, Forum.
Admin/Shared categories
This category contains code, objects and data that is shared between the modules.
| Category | Description |
|---|---|
| Includes | Included documents such as the header, footer and main menu. |
| LiveObjects | Live Objects |
| CSS | CSS (style sheets) that are used globally of for specific areas. |
| Images | Binary files (images) |
| Templates | Templates to describe the layout (number of columns, placements, widths etc.) of different pages |
Admin/Modules categories
This level is probably the most important level in terms of structure for the developers. This category usually contains categories corresponding to the functions of the website. Examples: News, Articles, Voting and Forum. Every module has the following categories:
| Category | Description |
|---|---|
| Editing Templates | The editing templates used for the module. |
| Presentation Templates | The presentation templates used for the module. |
| HTML | Regular HTML pages that are used but not edited by editors. |
| Included | HTML pages without meta/data that are inserted but not edited by editors. |
| Images | Binary files (images) |
| Templates | Templates to describe the layout (number of columns, placements, widths etc.) of different pages |
Language categories (Eng, Sve...)
Each language can be placed in a separate unit. This makes it easy to define MLC and to create language-specific functionality. Also, it becomes easy to define language specific document setting such as character encoding.
Each category usually only contain regular documents, and may contain other categories for documents or images. But there should be no templates, LiveObjects or similar in these categories. The Language categories are intended to let editors manage the information on the web site. The presentation, external references and other technical details should only be available to administrators and developers.
IFS Example
The IFS below demonstrates a typical IFS for a website and a News module. Files are in italics.
Admin
Shared
Includes
CSS
Images
WebDesign
LiveObjects
News listing, right column
User Controls
Modules
News
Editing Templates
Edit template News
Edit template Publishers
Presentation Templates
PT News
No Metadata
PT Newslisting
Includes
News listing
User Controls
News flash
Eng
News
A news article
Lookup
Publishers
Aftonbladet
Sve
Nyheter
En nyhetsartikel
Configuration
News
Settings